|
JIRA 4.4 : JIRA WAR Configuration Overview
This page last changed on Jun 16, 2011 by ggaskell.
While the individual server install guides provide specific instructions, it is useful to have an overall conceptual overview of what the configuration process involves. Webapp layoutAfter downloading and extracting the JIRA WAR web application archive, your are presented with a directory containing: appendcp.bat build.bat build.sh build.xml edit-webapp/ etc/ licenses/ readme.txt src/ tools/ updater/ webapp/
Database ConfigurationIf you are setting up a new installation of JIRA WAR, the JIRA setup wizard will configure a direct JDBC connection to a new JIRA database. Upon completing the setup wizard, your database configuration will be defined and saved into a dbconfig.xml file located at the root of your JIRA Home Directory.
Transaction Manager configurationJ2EE-based applications also rely on a Transaction Manager to coordinate updates across multiple databases. While JIRA currently does not use this facility, JIRA's underlying library (OfBiz) still requires a transaction manager object. As with database connections, this is provided by the application server as a javax.transaction.UserTransaction object, which is looked up via JNDI. Summing Up Database Configuration for JIRA WARHence, JIRA needs to know at least three things:
Points 1 and 2 are configured in the entityengine.xml file, as described in Configuring the Entity Engine for JIRA. An editable copy of the entityengine.xml file is located in edit-webapp/WEB-INF/classes. Point 3 is configured in the dbconfig.xml file. The content of this file is generated after completing the JIRA setup wizard. User management configurationJIRA stores all user profiles in a database table. Occasionally, integration with external user management systems like LDAP is required. See The LDAP Integration guide for more information. |
| Document generated by Confluence on Aug 18, 2011 23:17 |